<rss version="2.0" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/">
    <channel>
        <title>Business Analyst Community &amp; Resources | Modern Analyst</title> 
        <link>https://modernanalyst.com</link> 
        <description>RSS feeds for Business Analyst Community &amp; Resources | Modern Analyst</description> 
        <ttl>60</ttl> <item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3066/Facilitated-Workshops--When-Why.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=3066</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=3066&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Facilitated Workshops - When &amp; Why</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3066/Facilitated-Workshops--When-Why.aspx</link> 
    <description>The &amp;ldquo;good old workshop&amp;rdquo;. As a business analyst practitioner and trainer I often get asked the question &amp;ldquo;should we use a workshop?&amp;rdquo; quickly followed by &amp;ldquo;how do we run it?&amp;rdquo;. This article addresses the first question (subsequent articles will look at the second).</description> 
    <dc:creator>pddean</dc:creator> 
    <pubDate>Fri, 05 Sep 2014 04:40:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:3066</guid> 
    <enclosure url="https://modernanalyst.com:443/Portals/0/Public%20Uploads/Facilitated%20Workshops%20-%20When%20and%20Why.pdf" length="394905" type="application/octet-stream" />
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2685/Writing-Better-Requirements.aspx#Comments</comments> 
    <slash:comments>2</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=2685</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=2685&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Writing Better Requirements</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2685/Writing-Better-Requirements.aspx</link> 
    <description>There’s little argument that investigating and identifying business needs (i.e. requirements) is a critical task of business analysis. However it’s of little use correctly identifying business needs if we can’t then effectively document them - to the clients who will be paying for the solution and to the developers who will be building it. In today’s time poor world we need to address both audiences in a single document.</description> 
    <dc:creator>pddean</dc:creator> 
    <pubDate>Sun, 11 Aug 2013 10:46:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:2685</guid> 
    <enclosure url="https://modernanalyst.com:443/Portals/0/Public%20Uploads%204/Writing_Better_Requirements.pdf" length="566820" type="application/pdf" />
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2347/The-BAs-Journey--From-a-Current-to-a-Future-State.aspx#Comments</comments> 
    <slash:comments>3</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=2347</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=2347&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>The BA&#39;s Journey - From a Current to a Future State</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2347/The-BAs-Journey--From-a-Current-to-a-Future-State.aspx</link> 
    <description>Many words have been written about the process of business analysis and how it can be performed on different types of projects. There are a multitude of tools and techniques which can be used plus methodologies and frameworks to suit a wide variety of circumstances. This makes it all too easy to get absorbed in the day-to-day detail and forget about the real purpose of business analysis – to fix a problem or provide the organisation with a new capability.</description> 
    <dc:creator>pddean</dc:creator> 
    <pubDate>Mon, 24 Sep 2012 08:07:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:2347</guid> 
    <enclosure url="https://modernanalyst.com:443/Portals/0/Public%20Uploads%203/The_Business_Analyst_Journey_From_a_Current_to_a_Future_State.pdf" length="594805" type="application/pdf" />
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2111/Data-Modelling-Object-Oriented-Development.aspx#Comments</comments> 
    <slash:comments>4</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=2111</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=2111&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Data Modelling &amp; Object Oriented Development</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2111/Data-Modelling-Object-Oriented-Development.aspx</link> 
    <description>At some stage in their working life, every business analyst will have some involvement with data modelling. They may need to model how data is (or will be) used or - if they only deal with requirements investigation - then someone else in the team will need to verify that the data to support new functions will be available.</description> 
    <dc:creator>pddean</dc:creator> 
    <pubDate>Mon, 19 Dec 2011 05:23:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:2111</guid> 
    <enclosure url="https://modernanalyst.com:443/Portals/0/Public%20Uploads%203/Data_Modelling_and_Object_Oriented_Development.pdf" length="467770" type="application/pdf" />
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/1851/From-Mission-Statement-to-Business-Process.aspx#Comments</comments> 
    <slash:comments>1</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=1851</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=1851&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>From Mission Statement to Business Process</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/1851/From-Mission-Statement-to-Business-Process.aspx</link> 
    <description>Most business analysts will never interview a CEO and many don’t understand how a company’s real objectives cascade down to the little bit of requirements they’re doing for a particular system.
How does my system fit into the company’s business strategy? What is my role in the big picture?</description> 
    <dc:creator>pddean</dc:creator> 
    <pubDate>Thu, 26 May 2011 11:26:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:1851</guid> 
    <enclosure url="https://modernanalyst.com:443/Portals/0/Public%20Uploads%202/From_Mission_Statement_to_Business_Process.PDF" length="533359" type="application/pdf" />
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/1625/Just-Enough-Documentation.aspx#Comments</comments> 
    <slash:comments>1</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=1625</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=1625&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Just Enough Documentation</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/1625/Just-Enough-Documentation.aspx</link> 
    <description>Is documentation a blessing or a curse? If you’re working on an agile project does it get in the way? If you’re updating a core system that runs your company’s business, are you cursing the analyst who didn’t adequately document all the business functionality? Is today’s agile project tomorrow’s core system?</description> 
    <dc:creator>pddean</dc:creator> 
    <pubDate>Mon, 29 Nov 2010 05:01:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:1625</guid> 
    <enclosure url="https://modernanalyst.com:443/Portals/0/Public%20Uploads%202/Just_Enough_Documentation_Phil_Dean.pdf" length="485537" type="application/pdf" />
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/1489/How-to-Deliver-a-Recommendation.aspx#Comments</comments> 
    <slash:comments>2</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=1489</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=1489&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>How to Deliver a Recommendation</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/1489/How-to-Deliver-a-Recommendation.aspx</link> 
    <description>Like it or not, every business analyst will have to stand up in front of a group and present. The group might be your business clients, the project stakeholders or just your fellow team members but for many people, one of two things will happen: it will frighten the life out of them OR they’ll umm and ah their way through, sending the audience to sleep.&amp;#160; Why is this so?
&amp;#160;</description> 
    <dc:creator>pddean</dc:creator> 
    <pubDate>Wed, 18 Aug 2010 00:45:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:1489</guid> 
    <enclosure url="https://modernanalyst.com:443/Portals/0/Public%20Uploads/How_to_Deliver_a_Recommendation.PDF" length="196394" type="application/pdf" />
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/1264/What-is-a-Business-Analyst.aspx#Comments</comments> 
    <slash:comments>2</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=1264</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=1264&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>What is a Business Analyst? </title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/1264/What-is-a-Business-Analyst.aspx</link> 
    <description>Today the term Business Analyst is synonymous with a career in the IT industry but the most successful and valuable analysts are those who understand the &#39;business&#39; rather than those who understand IT. So what exactly is a Business Analyst? What is the Business Analyst’s role? What is the best background for this job? What skill set is required? What type of person is the best fit? What training is required and available?</description> 
    <dc:creator>pddean</dc:creator> 
    <pubDate>Mon, 15 Mar 2010 04:01:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:1264</guid> 
    <enclosure url="https://modernanalyst.com:443/Portals/0/Public%20Uploads/What_is_a_Business_Analyst_Updated_2010.pdf" length="196104" type="application/pdf" />
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/1263/How-to-Interview-Your-Boss.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=1263</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=1263&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>How to Interview Your Boss</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/1263/How-to-Interview-Your-Boss.aspx</link> 
    <description>&amp;#160;Ever had to interview your boss – or a divisional general manager – or the managing director of a key customer? What about a politician or a senior executive in a government department? All these scenarios can be nerve racking, yet they’re something a business analyst may be required to do on a regular basis.</description> 
    <dc:creator>pddean</dc:creator> 
    <pubDate>Thu, 18 Feb 2010 05:01:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:1263</guid> 
    <enclosure url="https://modernanalyst.com:443/Portals/0/Public%20Uploads/How_to_Interview_Your_Boss.PDF" length="139268" type="application/pdf" />
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/1160/The-Creative-Business-Analyst--Part-3-Making-Better-Decisions.aspx#Comments</comments> 
    <slash:comments>1</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=1160</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=1160&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>The Creative Business Analyst - Part 3, Making Better Decisions</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/1160/The-Creative-Business-Analyst--Part-3-Making-Better-Decisions.aspx</link> 
    <description>In this final paper of the series we look at decision making techniques – how to select the best idea from the many we’ve come up with – and how to justify our recommendation to our client, manager and peers.
&amp;#160;</description> 
    <dc:creator>pddean</dc:creator> 
    <pubDate>Mon, 16 Nov 2009 05:14:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:1160</guid> 
    <enclosure url="https://modernanalyst.com:443/Portals/0/Public%20Uploads/Creative_Business_Analyst_3.pdf" length="130150" type="application/pdf" />
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/940/The-Creative-Business-Analyst--Part-2-Generating-Solution-Ideas.aspx#Comments</comments> 
    <slash:comments>5</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=940</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=940&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>The Creative Business Analyst - Part 2, Generating Solution Ideas</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/940/The-Creative-Business-Analyst--Part-2-Generating-Solution-Ideas.aspx</link> 
    <description>A lot of people think that coming up with solutions to business problems is the hardest part about being a business analyst – particularly when working with a client who knows more about the business than you ever will. Don’t believe it, after all you’ve already made considerable progress in understanding the problem – and your understanding is based on level-headed analysis rather than a potentially emotional interpretation by your client.
Now it’s time to look for solutions – to be creative and think outside the square. In this paper we’ll offer a few tips and techniques for getting the creative juices flowing. We’ll show you that anyone can be creative and that solutions can come from the most unexpected places – you don’t have to be a subject matter expert to come up with valid, workable solutions to business problems.</description> 
    <dc:creator>pddean</dc:creator> 
    <pubDate>Mon, 25 May 2009 03:51:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:940</guid> 
    <enclosure url="https://modernanalyst.com:443/Portals/0/Public%20Uploads/Creative_Business_Analyst_2.PDF" length="279400" type="application/pdf" />
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/939/Golden-Rules-for-Business-Analysts.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=939</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=939&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Golden Rules for Business Analysts</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/939/Golden-Rules-for-Business-Analysts.aspx</link> 
    <description>Like all professions, business analysis has its golden rules – rules that are fundamental to the design of successful business systems. They might seem like common sense but it’s surprising how often we forget them and get ourselves into hot water.</description> 
    <dc:creator>pddean</dc:creator> 
    <pubDate>Mon, 25 May 2009 03:44:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:939</guid> 
    <enclosure url="https://modernanalyst.com:443/Portals/0/Golden_Rules_for_Business_Analysts.PDF" length="384609" type="application/pdf" />
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/623/What-is-a-Business-Analyst.aspx#Comments</comments> 
    <slash:comments>2</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=623</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=623&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>What is a Business Analyst?</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/623/What-is-a-Business-Analyst.aspx</link> 
    <description>Today the term Business Analyst is synonymous with a career in the IT industry but the most successful and valuable analysts are those who understand the &#39;business&#39; rather than those who understand IT. So what exactly is a Business Analyst? What is the Business Analyst’s role? What is the best background for this job? What skill set is required? What type of person is the best fit? What training is required and available? 

Each organisation seems to have its own ideas about the role, skills, responsibilities and expectations of the Business Analyst. Given the importance of the job, a common definition would assist both practitioners and employers. We explore some of the issues here. 

Written by Derrick Brown, IRM&#39;s Director and instructional designer, it shares first hand observations and experience gained from training thousands of Business Analysts since 1980, first in the UK and since 1984 in Australia.
Author: Derrick Brown</description> 
    <dc:creator>pddean</dc:creator> 
    <pubDate>Tue, 02 Dec 2008 02:15:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:623</guid> 
    <enclosure url="https://modernanalyst.com:443/Portals/0/Public%20Uploads/What_is_a_Business_Analyst.pdf" length="215514" type="application/pdf" />
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/622/Managers-Guide-to-User-Acceptance-Testing.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=622</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=622&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Manager&#39;s Guide to User Acceptance Testing</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/622/Managers-Guide-to-User-Acceptance-Testing.aspx</link> 
    <description>For most businesses and organisations, if IT stops, the business stops. Whenever a company turns on a new production line, opens a new retail store, launches a new product or provides a new service, there is invariably a new or modified IT system behind it. Going live is the culmination of time, effort, resources and finance. A problem-free IT system is the &amp;ldquo;acid test&amp;rdquo; of significant, often crucial investment.

Whilst the technical testing of IT systems is a highly professional and exhaustive process, testing of business functionality is an entirely different proposition. Does the system deliver the business functions that are required &amp;ndash; does it follow the company&amp;rsquo;s business rules &amp;ndash; does it support a government department&amp;rsquo;s obligations - does it cope with exceptions?

The people who have to make these decisions &amp;ndash; to accept or reject the new system &amp;ndash; are the business users. It is therefore critical to get the business user involved in testing and not rely only on the technicians. In this paper we explore the rationale behind User Acceptance Testing (UAT), why it is so important, and how best to go about it.

Author: Jan Kusiak
</description> 
    <dc:creator>pddean</dc:creator> 
    <pubDate>Tue, 02 Dec 2008 02:13:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:622</guid> 
    <enclosure url="https://modernanalyst.com:443/Portals/0/Public%20Uploads/Managers_Guide_to_User_Acceptance_Testing.pdf" length="244388" type="application/pdf" />
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/620/UML--Business-Context.aspx#Comments</comments> 
    <slash:comments>2</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=620</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=620&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>UML - Business Context</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/620/UML--Business-Context.aspx</link> 
    <description>“Where does UML fit?” is a common question among new (and not so new!) business analysts. We all know that the M stands for modelling but beyond this, perceptions start to differ. In its current form (V2.0) UML consists of 13 diagram types all of which provide a different view of a system. 

In this article we’ll take a brief look at which of the 13 diagrams are of most relevance for us and how they fit together...
Author: Jan Kusiak</description> 
    <dc:creator>pddean</dc:creator> 
    <pubDate>Tue, 02 Dec 2008 02:04:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:620</guid> 
    <enclosure url="https://modernanalyst.com:443/Portals/0/Public%20Uploads/UML_Business_Context.pdf" length="238092" type="application/pdf" />
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/592/Stakeholder-Communications--Pictures-not-Words.aspx#Comments</comments> 
    <slash:comments>5</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=592</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=592&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Stakeholder Communications - Pictures not Words</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/592/Stakeholder-Communications--Pictures-not-Words.aspx</link> 
    <description>Many people on our Business Analysis workshop ask why we use dataflow diagrams (DFDs). Why not Use Case…or even BPMN? After all DFDs have been around for 20 years, surely the world has moved on?
Well, has it? The primary purpose of a business analyst is to communicate – to stakeholders and to solution providers – and when it comes to communication we all know that pictures (diagrams) are much more effective and less ambiguous than words. Remember the phrase &quot;A picture is worth a thousand words&quot;. The question is – which type of diagram best suits our needs? In this article, written by IRM&#39;s Training Services Manager Jan Kusiak, we’ll look at using diagrams for stakeholder communications.

Author: Jan Kusiak
</description> 
    <dc:creator>pddean</dc:creator> 
    <pubDate>Sat, 01 Nov 2008 00:37:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:592</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/591/The-Creative-Business-Analyst--Part-1.aspx#Comments</comments> 
    <slash:comments>3</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=591</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=591&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>The Creative Business Analyst - Part 1</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/591/The-Creative-Business-Analyst--Part-1.aspx</link> 
    <description>Many of us are familiar with the process of business analysis – start by gathering requirements from stakeholders then turn them into a specification which developers can understand. These days however, we need to do more than just document the requirements.
We need to work with stakeholders and business users to understand their systems and analyse their problems – why do you do it this way, why not that way? This is the real value add that the analyst brings to the table. It means challenging the status quo, pushing the boundaries, looking for alternative or creative solutions.
To develop a solution - unless we’re very lucky - we first need to understand the problem that drives the need. In this paper we&#39;ll look at how to understand and define business problems – part 2 will look at how to generate solution ideas and part 3 will cover how to choose the best ones.
Author: Jan Kusiak</description> 
    <dc:creator>pddean</dc:creator> 
    <pubDate>Sat, 01 Nov 2008 00:29:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:591</guid> 
    <enclosure url="https://modernanalyst.com:443/Portals/0/Public%20Uploads/Creative_Business_Analyst_1.pdf" length="111768" type="application/pdf" />
</item>

    </channel>
</rss>